This requires a documentation change, including breaking change instructions.

I've pushed an attempt at documenting the changes.
@Wimads please let me know what you think.

@Wimads Can you update the desmos image and link for the new formula?

Note for self, from Discord:

Also, @burkfers, I think the ranges/steps for keycodes and via might need to be adjusted. Something like this would do I think:

Variable:    |  Range:      |  Step:
-------------+--------------+--------
TAKEOFF      |  0.50 - 5.00 |  0.01
GROWTH_RATE  |  0.01 - 5.00 |  0.01
OFFSET       |  0.0  - 15.0 |  0.1   
LIMIT        |  0.00 - 1.00 |  0.01

Can you explain this part @finrod09 ?
https://github.com/finrod09/qmk_userspace_features/blob/5cba04202c5d79945cf24fb32b361220446971cd/maccel/readme.md?plain=1#L118-L124

Throttling was necessary for myself to get my dragscroll implementation to work smoothly. Don't know what you mean with the linearity issue you describe here?

Also the line above (116) is duplication, I moved that to the bit above the preceding code block. Guess that got back in from a merge conflict.

Guess that got back in from a merge conflict.

Correct, I botched rebasing onto the spelling fix in maccel-dev. No content changes were intended.

Since it is likely #8 will merge before this, I will get another chance at rebasing correctly.

Edit: This was a result of this PR's history being convoluted and already containing merges that have to be manually resolved. We have let this PR linger too long and it has become bloated. A lesson for all involved, hopefully we'll do better next time :)

Guess that got back in from a merge conflict.

Correct, I botched rebasing onto the spelling fix in maccel-dev. No content changes were intended.

Since it is likely #8 will merge before this, I will get another chance at rebasing correctly.

Edit: This was a result of this PR's history being convoluted and already containing merges that have to be manually resolved. We have let this PR linger too long and it has become bloated. A lesson for all involved, hopefully we'll do better next time :)

Yeah I'm getting a lot of merge conflicts lately on this branch when syncing to my machine... Does this have to do with the spell check? All commits I did lately also got a spell check error.

But what about that throttling part in the readme? Is that also something that got back in accidentally over a merge, or was that intentional?